Repository navigation
Conversation
|
Important Review skippedToo many files! This PR contains 173 files, which is 73 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.
|
commit: |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requirement or Bug
Security auditfails onmainand every open PR: new advisories were published on 2026-11-09 (dompurify critical; undici, zod, electron, vue-i18n/@intlify, body-parser, follow-redirects, systeminformation, @azure/msal-node high; others moderate/low).Bug Reproduction Steps
pnpm auditonmainreports the advisories above.Root Cause
New upstream advisories against locked versions. Separately, the
pre-pushhook ran the test suite withGIT_DIR/GIT_INDEX_FILEexported, and tests that spawngitin temp dirs (tower, nix-hash) wrote commits and config into the real repository. Fundamental fix for both.Code Changes
pnpm.overrides: raise floors, each capped to its current major line (dompurify, undici, vue-i18n, @intlify/*, systeminformation, @azure/msal-node, body-parser, follow-redirects, fastify, fast-uri 3 and 4, serialize-javascript, qs, ip-address, vitest/@vitest/mocker~4.1.12, @hono/node-server^2.1.3).glob@>=9 <14.0.2to^14.0.2,minimatch@>=7 <11.0.1to^11.0.1(build and dev tooling only), andzod@3to^4.6.6for jimp (smoke-tested: blit, resize, crop, PNG encode).electron43.5.0 to 43.8.7 (desktop); zod catalog 4.4.3 to 4.6.7.auditConfig.ignoreGhsasgainsGHSA-gcqx-w48m-w2h4(deepmerge, no patched release; reached only via shadcn in the VS Code app).vitest.config.tsdeletes the repo-locatingGIT_*variables before workers fork, so hook-run tests cannot touch the real repository. Proved both ways withGIT_DIRpointed at a scratch repo: without the guard the scratch repo gets a moved HEAD anduser.name = Tower Test; with it, nothing changes.type: ["string","null"]; without this the manifests would degrade toany. Regenerated manifests are byte-identical to the committed ones.flake.nixpnpmDeps hash refreshed; web bundle rebuilt (lockfile is a bundle input).Behavior Changes and Affected Users
@hono/node-server2.x (MCP SDK HTTP transport)GIT_DIRand could write into the repoNo user-facing behavior change; no changeset. [skip changeset]
Coverage:
pnpm audit0 (one ignored low with no fix); typecheck, lint, sherif, vscode typecheck,nix build .#pythinker-codeall exit 0; full suite 18,619 passed, 3 failed: the stale wire manifest (fixed in this PR) and two known load-only timeouts that pass in isolation (148/148).Checklist
/approve).gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.